Session "Microsoft Security Essentials OOBE" stopped due to the following error: 0xC000000D using win 7 64bit over and over BSOD My event viewer has been coughing the error line above. It has lead to the feeling of a Carotid Artery leak of memory where my whole system slowly stops working till BSOD. Windows Explorer just stops working then Death. I HAVE HAD THIS HAPPEN MORE AND MORE, AND IT APPEARS TO BE A PROGRAM PROBLEM, ANYBODY ELSE HAVE THIS. IT HAS COST ME 2 DAYS WORK NOW. MIKE

Hi, When does the issue begin to occur? Since Windows system uses separated user mode and kernel mode memory space, stop errors are usually caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). Please refer to the following steps to troubleshoot the issue. 1. Boot the computer in Clean Boot for a test. 2. Temporarily disable all unnecessary hardware devices in Device Manager, such as Modem, sound card or external device. For detail steps, we can refer to the link below: Device Clean Boot 3. Upgrade the virus definition, run antivirus program and perform a full scanning. If the issue persists, please upload the minidump file (%systemroot%\minidump) to SkyDrive ( www.skydrive.live.com ), then share the link to me. I will be glad to assist you to analysis the data. Thanks, Novak

I'm having the exact problem as the original poster. If you wouldn't mind analyzing my dump file I would really love to know what's causing my daily BSOD on my Win 7 64 bit os. The link is: http://cid-f264f5759e0fb183.office.live.com/browse.aspx/.Public Thanks, Bruce

I'm having the exact problem as the original poster. If you wouldn't mind analyzing my dump file I would really love to know what's causing my daily BSOD on my Win 7 64 bit os. The link is: http://cid-f264f5759e0fb183.office.live.com/browse.aspx/.Public Thanks, Bruce Hey Bruce, Looking at your minidump, the faulty module is probably NETw5s64.sys which searching up shows all kinds of nasty BSODs. http://www.google.com/search?q=NETw5s64.sys Mike, can you provide a minidump?

I am getting the same sets of problems, but I can never find the minidump program. I look in the windows/minidump folder, but that directory is not there and no .dmp files exists on the computer. But I am getting BSODs. I really want to track the culprit. Hard drive, memory scan, and checkdisks all come out fine. Log Name: Microsoft-Windows-Kernel-EventTracing/Admin Source: Microsoft-Windows-Kernel-EventTracing Date: 8/22/2011 3:17:43 AM Event ID: 3 Task Category: Session Level: Error Keywords: Session User: SYSTEM Computer: XavierMorganPC Description: Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" /> <EventID>3</EventID> <Version>0</Version> <Level>2</Level> <Task>2</Task> <Opcode>14</Opcode> <Keywords>0x8000000000000010</Keywords> <TimeCreated SystemTime="2011-08-22T08:17:43.736814500Z" /> <EventRecordID>34</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="200" /> <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel> <Computer>XavierMorganPC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="SessionName">Microsoft Security Client OOBE</Data> <Data Name="FileName">C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl</Data> <Data Name="ErrorCode">3221225485</Data> <Data Name="LoggingMode">5</Data> </EventData> </Event>

I'm having the exact problem as the original poster. If you wouldn't mind analyzing my dump file I would really love to know what's causing my BSOD on my Win 7 64 bit os. The link is: https://skydrive.live.com/?cid=d1aecb809a5fb11b&sc=documents&id=D1AECB809A5FB11B%21227# Thanks very much

I also have runned into this problem: ----------------------------- Loggnamn: Microsoft-Windows-Kernel-EventTracing/Admin Källa: Microsoft-Windows-Kernel-EventTracing Datum: 2011-09-12 08:42:23 Händelse-ID: 3 Aktivitetskategori:Session Nivå: Fel Nyckelord: Session Användare: SYSTEM Dator: Tomas-PC Beskrivning: Sessionen "Microsoft Security Client OOBE" stoppade på grund av följande fel: 0xC000000D Händelsens XML-data: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" /> <EventID>3</EventID> <Version>0</Version> <Level>2</Level> <Task>2</Task> <Opcode>14</Opcode> <Keywords>0x8000000000000010</Keywords> <TimeCreated SystemTime="2011-09-12T06:42:23.128030900Z" /> <EventRecordID>10</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="200" /> <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel> <Computer>Tomas-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="SessionName">Microsoft Security Client OOBE</Data> <Data Name="FileName">C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl</Data> <Data Name="ErrorCode">3221225485</Data> <Data Name="LoggingMode">5</Data> </EventData> </Event> -------------------------------------------- Thanks Tomas By helping others I help myself

Nudge,,, Can someone look at my .dmp file?

I'm having the same issue and have tried several fixes that were suggested (uninstalled wireless card, deleted specific files popping up in my error logs) however when I tried to install the debugging tools to check my actual dump files I'd immediately BSOD. Could you look at them and help me out on this issue? Thanks, JeC https://skydrive.live.com/redir.aspx?cid=22faf5298e2b217e&resid=22FAF5298E2B217E!158&authkey=5HdQPfEIYPc%24

please can you check my file https://skydrive.live.com/redir.aspx?cid=1f7d587977721379&resid=1F7D587977721379!168 i got the same problem regards,

Hey, I installed my computer few days ago and i do have few times a day a restart but without a BSOD, minidump file or a notice in the event viewer. In the event viewer i do have the same error as you have but i do not know for sure that this is related to the restarts. Because it is a new computer i wanted to now if this is the same problem as you have or maybe i do have a hardware problem... Thanks, Nir

I am having the same problem... I am receiving phone support from Microsoft but the support engineer doesn't have a clue. I agreed to monitor until next weekend when he wants to have me re-install the O/S (64-bit Win 7 Pro). I don't believe this will solve the problem based on other posts. Observations: I have been manually updating MSE paying particular attention to the release date of the new definitions as they become available via Windows Update. What I notice is that the Windows Update is release as an "Optional" update which will not occur automatically. I believe MSE detects the availability of each new update and shuts down Behavior Monitoring. It appears that Real-Time Protection is still active but there seems to be a programming logic error with how MSE handles the availability of new virus definition updates which occur one or more times per day. I do not experience any other issues like BSOD or explorer hangs. The following error occurs along with the error above: Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection. PLEASE HELP IF YOU CAN!

I was having the same problem on my system a few months ago and it bugged me for weeks until I found a suggestion to remove Microsoft Security Essentials. Sounds counter-intuitive, but that fixed the problem. My friend called me the other day and asked if I could help him build a new computer, because his kept freezing and crashing unexpectedly. I checked out the event viewer and he had the exact same problems. Removed Security Essentials and voila, no more crashing. It appears that this problem has been ongoing for at least 6 months now and randomly affects different people and Microsoft still isn't addressing the problem.

I am also having the same issue. Daily: Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

i had the same issue but only when i run a program called advance system care 5 it started when it was reparing the reg then it crashed say system mem crash dump BLUE SCREEN it said to disable the anti virus well my anti virus is micro soft securty essit etc ... but if i didn`t run the advance system care it would not do that so its in the reg micro soft is their a patch or a tool to scan and repare the windows 7 64 bit reg file? if so please help me and others that have the same problem thank you( Doc haze )

I have symptoms similar to the ones described above. Sometimes BSOD, sometimes just freeze/crash. I have noticed that it happens more often than not when my system changes powerstate (I think) - that is, when I disconnect the AC from my laptop. Often, before the freeze, DWM is trying to restart/recover for a while. Between 30/12-2011 - 06/01-2012, I have 10 hits in MSE history on "worm:win32/conficker.B!inf" I don't know if it is related at all, but I don't remember having this issue before getting infected.

The problem 'Event ID 3' had attracted quite a few responses, and most of them were beating about the bush with no sure understanding of the problem. Since the page does not show that it has been solved, here is a 'solution', again without knowing for sure that it is the best: Either rename the file EppOobe.etl (in C > ProgramData > Microsoft > Microsoft Security Client > Support) as EppOobe.etl.old, or delete it, and reboot. Check the Support folder. If there was no other problem, Windows would have created a new EppOobe.etl file. Delete the file that had been renamed 'old'. May be, everyone already knows this solution by now, in which case this is an academic exercise.

The problem 'Event ID 3' had attracted quite a few responses, and most of them were beating about the bush with no sure understanding of the problem. Since the page does not show that it has been solved, here is a 'solution', again without knowing for sure that it is the best: Either rename the file EppOobe.etl (in C > ProgramData > Microsoft > Microsoft Security Client > Support) as EppOobe.etl.old, or delete it, and reboot. Check the Support folder. If there was no other problem, Windows would have created a new EppOobe.etl file. Delete the file that had been renamed 'old'. May be, everyone already knows this solution by now, in which case this is an academic exercise.